https://www.dynamisys.co.uk RSS feeds for Dynamisys 60 https://www.dynamisys.co.uk/Articles-Downloads/Articles/ID/106/Allow-access-to-IIS-Express-over-the-network#Comments 0 https://www.dynamisys.co.uk/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=723&ModuleID=1621&ArticleID=106 https://www.dynamisys.co.uk:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=106&PortalID=22&TabID=723 https://www.dynamisys.co.uk/Articles-Downloads/Articles/ID/106/Allow-access-to-IIS-Express-over-the-network I can never remember how to do this. (I used VS2017) Go into the .vs directory and edit applicationhost.config. Find the binding for the site you are interested in and change localhost to *.  So from bindingInformation="*:58904:localhost" to bindingInformation="*:58904:*" That's it done!  Of course you need to open suitable holes in any firewalls, but that is it for IIS Express  Same ideas mentioned here https://johan.driessen.se/posts/accessing-an-iis-express-site-from-a-remote-computer - his article seems to spell out the machine's IP address every time.  That seems not to be required for the binding (use the *).  Not sure about the other places.  I didn't need anything to allow access to the URL and I just turned off the firewall temporarily through sheer laziness. RichardHowells Thu, 17 Jan 2019 16:37:00 GMT f1397696-738c-4295-afcd-943feb885714:106 https://www.dynamisys.co.uk/Articles-Downloads/Articles/ID/91/Speed-up-for-Visual-Studio-Slow-Builds#Comments 0 https://www.dynamisys.co.uk/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=723&ModuleID=1621&ArticleID=91 https://www.dynamisys.co.uk:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=91&PortalID=22&TabID=723 https://www.dynamisys.co.uk/Articles-Downloads/Articles/ID/91/Speed-up-for-Visual-Studio-Slow-Builds The Windows Defender Antimalware executable slowed things a lot I ran task manager. As VS starts; Antimalware uses more CPU than VS. About 20x as much. Further research found Visual Studio's 'slave' processes, used to execute a build, also trigger Antimalware activity.  I configured Antimalware to not scan VS and it's slave processes. For those who prefer not to type them all into the ui; start a PowerShell prompt (I used elevated - not certain if that is required); and paste this in: Set-MpPreference -ExclusionProcess devenv.exe, TE.ProcessHost.Managed.exe, csc.exe, iisexpress.exe, msbuild.exe, vshost32-clr2.exe, vshost-clr2.exe, vshost32.exe, VBCSCompiler.exe, w3wp.exe Use completely at your own risk. Further information here Set-MpPreference.         I saw it reduce a small project build from 0m38s (no exclusions) to 0m06s (exclusions listed above). If you prefer using the Windows GUI; Go to Update & Security -> Settings -> Windows Defender. Open Defender and in the Settings selection, choose Exclusions, add the process names individually. RichardHowells Sat, 14 Jan 2017 13:22:00 GMT f1397696-738c-4295-afcd-943feb885714:91